Unfortunately, there's a number of issues that can cause problems, have a negative impact on the plugin's stability or just reduce the possible usefulness of the plugin:
- IDEADEV-11226: Completion in injection language fragment causes NPE
- IDEADEV-11227: No refactoring and navigation for language fragments injected into JSP custom tags
- IDEADEV-11212: Formatting of Injected Languages
- IDEADEV-11232: Injecting a Language into partial content of XML CDATA section fails
- Comment on
IDEADEV-8302: Why glued tokens are bad -
IDEA-9573: Injecting CSS language needs a special prefix and suffix to offer proper completion and error highlighting. It's required to configure the prefix "dummy_selector {" and suffix "}" to make this work for "raw" CSS e.g. in HTML "style"-Attributes. - If an injected fragment has a suffix (statically or dynamically) configured, it can happen that the highlighting of syntax errors is not visible in the editor. This is due to the way the plugin tries to avoid the "glued token" problem by adding a space character to the start of the suffix which can cause the syntax error to be disappear in the non-visible part of the fragment. The error stripe however will show that there is an error which can be further examined by using the Quick Edit Language feature.
- The Injection API does not allow to inject a language into Javadoc comments. This would have been great to support EJB-QL in XDoclet comments.
You can vote for and watch the open issues to get notified about their progress.